Right now we don't have a way to check that the clang-tidy package from the artifacts is newer than what we have locally, and hence errors might occur when we update it's integration/functionality.
We must develop a system in order to mitigate this.

This raises an interesting problem. If I work on a patch with the mozilla-central tree today, and you update clang-tidy or clang-format tomorrow, my tree is not going to know about that new version until I rebase. This gets worse on other branches, like beta, release or esr.

Nice observation Mike, I guess a more suited option here would be to present the possibility of downloading the latest clang-tidy artifact for the current repo version.